Clarifications about running dbt init --profile #4534
Conversation
Clarifications about running dbt init --profile
|
Hello!👋 Thanks for contributing to the dbt product documentation and opening this pull request! ✨ |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
victorrgez
changed the title
|
|
||
| When using `dbt init` to initialize your project, include the `--profile` flag to specify an existing `profiles.yml` as the `profile:` key to use instead of creating a new one. For example, `dbt init --profile`. | ||
| When using `dbt init` to initialize your project, include the `--profile` flag to specify an existing `profiles.yml` as the `profile:` key to use instead of creating a new one. For example, `dbt init --profile profile_name`. |
Resolved comments on PR
|
Sorry about the other two changes. They were the result of a misunderstanding. Thank you @aranke for your time reviewing the PR! |
|
Hi @aranke I'm not authorised to merge the PR, could you please do it or is there something else left to do first? thanks! |
|
hey @victorrgez and @aranke -- thank you so much for contributing and merging this PR for you now, Victor! |
Clarifications about running dbt init --profile
What are you changing in this pull request and why?
-Clarify the use of
dbt initwhen using an existingprofiles.ymlfile. The current docs are not clear enough and one may think you have to provide the path toprofiles.ymlas an argument, for example,dbt init --profile profiles.ymlwhen, in fact, you need to pass the actual name of your profile.REMOVED CHANGES:
-
Clarify that you cannot pass the--profileflag if you already have a dbt_project.yml file as the error returned (Can not init existing project with specified profile, edit dbt_project.yml instead) may be confusing-
Change VersionBlock version from 1.7 to 1.8Checklist
Review the Content style guide so my content adheres to these guidelines.
For docs versioning, review how to version a whole page and version a block of content.
Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
Need review of the doc changes as this is my first contribution